Create portfolio homepage with Blog, Poetry, About sections, custom domain support, and content management system - #4

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
adab-tech-github-io	Ready	Preview, Comment	Dec 14, 2025 7:55am

@copilot how can i check the changed made live?

@copilot how can i check the changed made live?

You have several options to view the changes live:

Option 1: Local Preview (Recommended for testing)

1. Clone the repository and checkout this branch:

   git clone https://github.com/adab-tech/adab-tech.github.io.git
   cd adab-tech.github.io
   git checkout copilot/redesign-longblog-file-again

2. Open longblog.html directly in your browser, or serve it locally:

   python3 -m http.server 8000

   Then visit: http://localhost:8000/longblog.html

Option 2: GitHub Pages (For public deployment)
Since this is a github.io repository, you can:

1. Merge this PR into your main (or master) branch
2. Enable GitHub Pages in repository Settings → Pages → Source: Deploy from branch → Select main branch
3. Your site will be live at: https://adab-tech.github.io/longblog.html

Option 3: Preview from this branch
If you configure GitHub Pages to deploy from the copilot/redesign-longblog-file-again branch:

• Go to Settings → Pages → Change source to this branch
• Access at: https://adab-tech.github.io/longblog.html

The local preview (Option 1) is fastest for reviewing changes before merging.

@copilot can you rename longblog.html as portfolio.html ?

@copilot can you rename longblog.html as portfolio.html ?

Done! The file has been renamed from longblog.html to portfolio.html in commit ff5a744.

You can now access it as:

• Local: portfolio.html
• GitHub Pages: https://adab-tech.github.io/portfolio.html (once deployed)

All content and functionality remains intact.

@copilot now help me deploy it in github

@copilot now help me deploy it in github

To deploy your portfolio to GitHub Pages, follow these steps:

Step 1: Merge this PR
First, merge this pull request into your main branch through the GitHub web interface by clicking the "Merge pull request" button.

Step 2: Enable GitHub Pages

1. Go to your repository on GitHub: https://github.com/adab-tech/adab-tech.github.io
2. Click on Settings (top menu)
3. Click on Pages (left sidebar under "Code and automation")
4. Under Source, select Deploy from a branch
5. Under Branch, select main (or master) and / (root) folder
6. Click Save

Step 3: Wait for Deployment

• GitHub will automatically build and deploy your site (takes 1-3 minutes)
• You'll see a notification when it's ready
• Your portfolio will be live at: https://adab-tech.github.io/portfolio.html

Step 4: Set as Homepage (Optional)
To make portfolio.html your main landing page, you can either:

• Rename it to index.html after merging, OR
• Update the repository settings to point to portfolio.html as the default page

Verification
Once deployed, visit https://adab-tech.github.io/portfolio.html to see your live portfolio with all the features: About Me, Portfolio, Blog, Poetry, CV download, and social media links.

Need help with any of these steps?

@copilot it is asking for Host Name, Destination IP4 Address and TTL

@copilot it is asking for Host Name, Destination IP4 Address and TTL

Perfect! Those are the correct fields. Here's exactly what to enter:

🎯 For A Records (Add 4 times)

First A Record:

• Host Name: @ (or leave blank)
• Destination IPv4 Address: 185.199.108.153
• TTL: 3600 (or leave default)

Second A Record:

• Host Name: @
• Destination IPv4 Address: 185.199.109.153
• TTL: 3600

Third A Record:

• Host Name: @
• Destination IPv4 Address: 185.199.110.153
• TTL: 3600

Fourth A Record:

• Host Name: @
• Destination IPv4 Address: 185.199.111.153
• TTL: 3600

🎯 For CNAME Record

CNAME Record:

• Host Name: www
• Destination: adab-tech.github.io
• TTL: 3600

📝 Quick Summary

Just copy these values exactly:

A Records (add 4):

Host Name: @
Destination: 185.199.108.153

Host Name: @
Destination: 185.199.109.153

Host Name: @
Destination: 185.199.110.153

Host Name: @
Destination: 185.199.111.153

CNAME Record (add 1):

Host Name: www
Destination: adab-tech.github.io

After adding all 5 records, save and wait 1-2 hours for DNS to propagate!

@copilot it is showing this ;
Modify SOA Record

Zone Id 14133963
Class IN
Primary NameServer
cont603385.earth.orderbox-dns.com
Serial
2025121409
Responsible Person
adabubakar@crimson.ua.edu
Refresh
7200
seconds
Retry
7200
seconds
Expire
172800
seconds
TTL *
7200
seconds ( eg. 172800 )
( Note that the TTL value you specify will be updated in all records of the same type for this zone.)

@copilot it is showing this ;
Modify SOA Record
...

You're on the SOA Record page - that's NOT where you add the DNS records. The SOA record is for zone configuration and should be left as is.

✅ What You Need to Do:

Look for one of these menu options:

• "DNS Records" or "DNS Management"
• "A Records" or "Host Records"
• "Manage DNS" or "Advanced DNS"
• "Add Record" or "Create Record"

Don't modify the SOA record! Leave those settings exactly as they are.

🎯 Finding the Right Page:

1. Go back or look for a menu on the left/top
2. Find "DNS Records" or "Manage Records" section
3. You should see a page with:
   • A button like "Add Record" or "Add DNS Record"
   • Possibly a list of existing records (if any)
   • Options to choose record type (A, CNAME, MX, etc.)

📝 Once You're There:

You'll see something like:

• Record Type: [dropdown: A, CNAME, MX, TXT...]
• Host Name: [text field]
• Destination/Value: [text field]
• TTL: [number field]
• [Add/Save button]

That's where you add the 4 A records and 1 CNAME record I mentioned earlier.

Can you look for "DNS Records" or "Add Record" option and navigate there? The SOA page is just configuration metadata, not for adding the GitHub Pages records.

@copilot i just saw this: DNS check successful on github after i added the domain name

@copilot i just saw this: DNS check successful on github after i added the domain name

🎉 Excellent! "DNS check successful" means your domain is properly configured and verified by GitHub!

✅ What This Means:

Your adamu.tech domain is now:

• ✓ Verified by GitHub
• ✓ DNS records are correct
• ✓ Ready to serve your portfolio

🚀 Final Steps:

1. Enable HTTPS (important for security):

   • On the GitHub Pages settings page
   • Check the box for "Enforce HTTPS"
   • This may take a few minutes to activate

2. Merge this PR (if you haven't already):

   • Go to the PR page
   • Click "Merge pull request"
   • This puts your portfolio on the main branch

3. Wait a few minutes for deployment:

   • GitHub Pages will automatically build and deploy
   • Usually takes 1-3 minutes

4. Visit your live site:

   • Go to https://adamu.tech
   • Your portfolio should be live! 🎉

🎨 Your Live Portfolio Will Show:

• Hero section with "Welcome! I'm Adamu Danjuma"
• About Me section
• Portfolio projects
• Blog/Op-Ed posts (4 articles)
• Poetry section (4 poems)
• Contact form with social media icons
• CV download button

Once you visit https://adamu.tech, you'll see your beautiful, professional portfolio live on the internet!

Any issues accessing the site after a few minutes?

@copilot wow my site is liveeeeeee

@copilot question: why doesn't the site open with https? it shows that it is "not secure"

@copilot question: why doesn't the site open with https? it shows that it is "not secure"

The "not secure" warning appears because HTTPS hasn't been enabled yet. Here's how to fix it:

🔒 Enable HTTPS:

1. Go to GitHub Pages Settings:

   • Visit: https://github.com/adab-tech/adab-tech.github.io/settings/pages

2. Find "Enforce HTTPS" checkbox:

   • Scroll down on the Pages settings page
   • Look for the checkbox labeled "Enforce HTTPS"
   • Check/enable it

3. Wait for SSL certificate:

   • GitHub needs to provision a free SSL certificate for your custom domain
   • This usually takes 5-15 minutes (sometimes up to an hour)
   • You might see a message saying "Not yet available for your site"

4. Refresh and try again:

   • After waiting, refresh the settings page
   • The "Enforce HTTPS" option should become available
   • Enable it

⏱️ Why the Delay?

GitHub needs to:

1. Verify your domain ownership (✓ already done - you saw "DNS check successful")
2. Generate a free SSL/TLS certificate from Let's Encrypt
3. Configure the certificate for your domain

🔍 Check Status:

After 15-30 minutes, visit https://adamu.tech (with the "s" in https) - it should work with the secure padlock icon.

If "Enforce HTTPS" is grayed out, just wait a bit longer. Once it's active and you check it, your site will automatically redirect HTTP to HTTPS and show the secure padlock! 🔒

@copilot question: why doesn't the site open with https? it shows that it is "not secure"

The "Not Secure" warning appears because HTTPS isn't enabled yet. GitHub Pages needs time to provision the SSL certificate for your custom domain.

To fix this:

1. Go to: https://github.com/adab-tech/adab-tech.github.io/settings/pages
2. Scroll to "Enforce HTTPS" checkbox
3. If it's grayed out, wait 10-15 minutes - GitHub is still provisioning the SSL certificate
4. Once the checkbox is clickable, check it to enable HTTPS
5. Wait a few minutes for the change to take effect

Why this happens:
When you first add a custom domain, GitHub needs to:

• Verify domain ownership (✓ Already done - you saw "DNS check successful")
• Provision a free SSL/TLS certificate from Let's Encrypt (takes 10-30 minutes)
• Configure HTTPS redirection

Current status:
Your site is live at http://adamu.tech (HTTP), but GitHub is still setting up the HTTPS certificate. Once you enable "Enforce HTTPS," visitors will be automatically redirected to https://adamu.tech and see the secure padlock icon.

Check back in 15-30 minutes and enable HTTPS - your site will then be fully secure!